-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: event bus related ADRs #40
Conversation
docs/decisions/0004-event-bus-as-extension-of-django-signals.rst
Outdated
Show resolved
Hide resolved
11399cc
to
c418767
Compare
@dianakhuang Pinging you about this PR. I think it is ready for a final review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Just had one last comment about some of the new things.
docs/decisions/0004-event-bus-as-extension-of-django-signals.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0004-event-bus-as-extension-of-django-signals.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0005-event-bus-support-forward-schema-evolution.rst
Outdated
Show resolved
Hide resolved
|
||
- The values can be: python primitives(int, str, dict, list ...), attrs decorated classes defined in openedx-events repository, or custom classes that have extensions defined in AvroAttrsBridge class. | ||
|
||
- Ideally, the values are attrs decorated classes, other types are supported for convenience. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm realizing now that when instantiating OpenEdxPublicSignal
we don't check for the data types. Maybe that's something we are interested in? So we are entirely sure the event it's using a data attr class
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mariajgrimaldi: I'm not clear on the validation proposal. I don't think we will be pursuing anything at this time, but if you see an important gap and you want to discuss more, feel free to explain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initial comments for our discussion.
docs/decisions/0004-event-bus-as-extension-of-django-signals.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0004-event-bus-as-extension-of-django-signals.rst
Outdated
Show resolved
Hide resolved
Hi, I am going to do many changes to this PR based on review. Please hold off on further review for a bit. |
@robrap This PR is ready for another review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the work on these @jinder1s.
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0005-event-schema-serialization-and-evolution.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0005-event-schema-serialization-and-evolution.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0005-event-schema-serialization-and-evolution.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0005-event-schema-serialization-and-evolution.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0005-event-schema-serialization-and-evolution.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0005-event-schema-serialization-and-evolution.rst
Outdated
Show resolved
Hide resolved
3d79a67
to
77c7c15
Compare
The change log had various formatting bugs due to the inconsistent use of both `_` (underscore) and `-` (hyphen). The new format only uses hyphens. Added `=` for the top-level. Finally, reversed `-` and `~` to be more consistent with other docs, like the ADRs in this repo.
54ef495
to
ecdd612
Compare
@dianakhuang: Can I get your review to get this over the line. Sorry - there is a lot going on in this PR. Let me know if anything should be split out. Here is an overview of the changes:
Additionally, I made the following minor changes (in separate commits):
Separately, I asked tCRIL to publish these docs to readthedocs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had some confusion about some of the phrasing in the first ADR.
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
@dianakhuang: Thanks. Ready for re-review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One typo to fix, but then I think you are good to merge.
docs/decisions/0004-external-event-bus-and-django-signal-events.rst
Outdated
Show resolved
Hide resolved
Adds two new ADRs. 1. External event bus and Django Signal events: details the relationship between the new external event bus events and the existing internal Django Signal events. 2. Event schema serialization and evolution: details how an event schema will be used for event schema evolution. ARCHBOM-2010
Moving event schema ADR from sub-decision of the Event Bus ADR to the openedx-events repo, so it can live side-by-side with other related decisions.
The event schema ADR was first moved from the OEP repo without changes, and this commit makes some minor tweaks to make it work inside this repo. It also adds some notes about the CLoudEvents specification.
Renamed how_tos directory to align with OEP-19.
Make sections in the docs index for the ADRs (Decisions) and How-Tos.
c83aad7
to
6dadd8b
Compare
@jinder1s: We finally merged it! 🎉 |
@robrap Hallelujah! It's Done! haha |
Yes. Thanks for all your work on this @jinder1s. You are missed. |
Hi, @robrap! All these ADRs have been provisional for some time now, should we change their status? |
@mariajgrimaldi: Maybe https://github.com/openedx/openedx-events/blob/main/docs/decisions/0004-external-event-bus-and-django-signal-events.rst is the only one that wasn't updated? It can move to accepted. Thank you. Let me know if you will take care of that. |
@robrap: I will! Thank you. |
Some of the ADRs that came out of following issue discussions:
https://github.com/eduNEXT/openedx-events/issues/38
https://github.com/eduNEXT/openedx-events/issues/39
These adrs mostly cover issue 38, but do add some info from issue 39.